-
Notifications
You must be signed in to change notification settings - Fork 16
set $EPREFIX correctly for RISC-V clients
#92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Tested in a container on the RISC-V cluster: |
|
And for an x86_64 client, by using the dir of this branch: |
ocaisa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
Deployment PR merged |
With #80 being merged, the bot almost got to the point where it would actually install software, but it failed on this line: https://github.com/EESSI/software-layer-scripts/blob/main/EESSI-install-software.sh#L229.
It turned out that
$EPREFIXwas set to/cvmfs/dev.eessi.io/riscv/versions/2025.06/compat/linux/riscv64, resulting in:This PR fixes it by introducing an additional variable for the compat layer prefix, which can then be overridden for the different RISC-V versions (20240402 has its own compat layer, 2025.06 won't have that).